What is the Bug in the Received Email Triggers for Outlook Identified in the Github Issue #21159?

user-1 · June 25, 2026, 5:13pm

This topic was automatically generated from Slack. You can find the original thread here.

We discovered a bug on the Received Email triggers for outlook - based on the source’s timestamp queuing: [BUG] Shared Microsoft Inbox Trigger timestamp bug causing dropped emails · Issue #21159 · PipedreamHQ/pipedream · GitHub

user-1 · June 25, 2026, 5:13pm

Thanks for reporting this, makes sense to me, will have a look in more detail

user-1 · June 25, 2026, 5:13pm

what’s the actual app and component name? I hadn’t noticed initially but it’s not mentioned in the GH issue

user-1 · June 25, 2026, 5:13pm

github.com/PipedreamHQ/pipedream

components/microsoft_outlook/sources/new-email-in-shared-folder/new-email-in-shared-folder.mjs

master

import md5 from "md5";
import { DEFAULT_POLLING_SOURCE_TIMER_INTERVAL } from "@pipedream/platform";
import microsoftOutlook from "../../microsoft_outlook.app.mjs";
import sampleEmit from "./test-event.mjs";

export default {
  key: "microsoft_outlook-new-email-in-shared-folder",
  name: "New Email in Shared Folder Event",
  description: "Emit new event when an email is received in specified shared folders.",
  version: "0.0.19",
  type: "source",
  dedupe: "unique",
  props: {
    microsoftOutlook,
    db: "$.service.db",
    timer: {
      type: "$.interface.timer",
      default: {
        intervalSeconds: DEFAULT_POLLING_SOURCE_TIMER_INTERVAL,
      },

This file has been truncated. show original

user-1 · June 25, 2026, 5:13pm

Thanks, linked a PR to address the issue

user-1 · June 25, 2026, 5:13pm

to get the latest version should we just re-create a new trigger?

user-1 · June 25, 2026, 5:13pm

Yes